Flarelink — your backend, on your own Cloudflare

How it works

Three steps to a backend that's yours.

Connect your Cloudflare

Paste a scoped Cloudflare API token. Flarelink only touches resources when you explicitly ask it to provision or change one.

Create a project

One click provisions an auth Worker, a D1 database for your users, and a KV namespace for sessions — all in your account, with the keys shown to you once. Add R2 storage later when you need files.

Build and ship

Install @flarelink/client and call auth, storage, from(…) with one URL and one service key. Manage it all in one dashboard.

Everything an app backend needs

Auth is the hard part. We made it the centerpiece.

A complete, verifiable auth system — with a database, object storage, and email wired in around it. All running on your own Cloudflare resources, managed in one place.

Auth

The moat

Drop-in authentication with sessions, social providers (Google + GitHub), magic links, password reset, and email verification. The auth Worker is source-available and deployed to your account — so you can rebuild it byte-for-byte and confirm what's running. Sessions live in KV, so auth checks are sub-millisecond and cheap.

OAuth Magic links Sessions in KV Editable templates Source-available Verifiable

Auth docs Verify the Worker

// browser — no service key needed
await flarelink.auth.signInWithSocial("google")
await flarelink.auth.signIn({ email, password })

const me = await flarelink.auth.getMe()  // User | null

Database

A real SQL database on Cloudflare D1 — visual table + schema editor, a multi-tab SQL console, and a type-safe client.

SQLite Table editor Type-safe SDK

Storage

Object storage on R2 with signed upload URLs and zero egress fees. Files go browser → bucket; Flarelink stays out of the byte path.

S3-compatible Signed URLs No egress

Email

Password resets, magic links, and verification through Cloudflare Email Sending or Resend. Editable templates with live previews.

Transactional Templates Resend

Verify, don't trust

Rebuild our auth Worker and diff it against what's deployed in your account.

The auth Worker is source-available (FSL-1.1-MIT). Reproducible builds and published hashes mean one command proves the bytes running in your account match the published source — no need to take our word for it.

npx @flarelink/verify --url \
  https://auth.yourapp.com
✓ deployed matches published v0.3.0

Reproducible builds @flarelink/verify Activity log What the token can touch Full trust page

One install. Four services.

From zero to a wired backend.

One typed SDK with the same surface as the platforms you already know — auth, storage, from(…). The dashboard provisions everything in your account; the SDK speaks to it directly.

~/acme

$ npm install @flarelink/client

# 8.2 KB · zero runtime deps

✓ auth sessions · OAuth · magic links

✓ database D1 · table editor + SDK

✓ storage R2 · signed upload URLs

✓ email CF Email or Resend

ready · open the dashboard

You own it

The infrastructure is yours. We just keep it calm.

Most backend platforms rent you their servers and hope you never leave. Flarelink runs entirely on your Cloudflare account, so leaving is a non-event — which is exactly why people stay.

See exactly what we can touch — and revoke it anytime

Your data sits in your D1 and R2 — we hold a scoped token, never a copy.

Cancel anytime and your backend keeps running. There's nothing to migrate off.

You pay Cloudflare directly for usage. Flarelink is a flat fee — no markup on egress.

FAQ

The honest answers.

How does Flarelink see my account?

You create a scoped Cloudflare API token and paste it in. Flarelink uses it to read and provision your D1, R2, Workers, KV, and Email through Cloudflare's public APIs. It only writes when you explicitly provision or change a resource in the dashboard.

Where does my data actually live?

In your own Cloudflare account. Auth users and app data go in your D1 database; files go in your R2 bucket. Flarelink stores configuration and a scoped token — never a copy of your data.

Is this an official Cloudflare product?

No. Flarelink is an independent backend platform built on Cloudflare's public APIs. We're not affiliated with or endorsed by Cloudflare.

What happens if I cancel?

Your backend keeps running — it's your infrastructure. You lose the Flarelink dashboard and SDK access, but the database, bucket, auth Worker, and email config stay exactly where they are.

Do I need all four services?

No. Use only what you need — run Flarelink just for auth, or just to manage an R2 bucket. The dashboard shows what you use and stays quiet about the rest.

Your backend, on your own Cloudflare.